Wikipedia:Interface administrators' noticeboard

Welcome to the interface administrators' noticeboard
This is the interface administrator noticeboard, for discussion of interface administrators and coordination of edits to the interface. Currently only interface administrators can undelete JS/CSS pages, if you have an uncontroversial undelete or deleted version retrieval request, please list it below. Any administrator can delete JS/CSS/JSON pages, for speedy deletions just use a CSD template on the page or its talk page. Individual requests for edits to interface or user JavaScript/CSS pages should continue to be made on their respective talk pages.
Click here to start a new discussion

2 interface-protected edit requests v·h
Page Tagged since Protection level Last protection log entry MediaWiki:Gadget-WatchlistBase.css (request) 2024-03-02 23:26 Site CSS page (log) MediaWiki:Gadget-watchlist-notice-core.js (request) 2024-03-02 23:26 Site JS page (log)
Updated as needed. Last updated: 15:23, 20 May 2024 (UTC)

Pennsylvania and weird message

Hey everyone, I'm not sure where to ask but this feels like the best place to do so. A work colleague has just brought up to my attention the page Pennsylvania, where if you are logged out, a big message saying "User:CheezDeez ON TOP" appears. That particular user has been indefinitely blocked for sockpuppeting. I am unable to find anything like this in the source code and it only happens if you're logged out, so I presume this comes from some HTML/JS running somewhere and putting that there. It's the most bizarre thing I've ever seen on any Wikiproject and I'm not sure how to proceed, but I think you guys might have the best options on solving this. Thank you for taking a look and @ me if you need anything or if you solve this issue. I'm curious where it's coming from. KormiSK (talk) 18:03, 28 April 2024 (UTC)

This is cached template vandalism. See WP:VPT#Strange bug on Flag of Russia article. A null edit should sort it. Izno (talk) 18:11, 28 April 2024 (UTC)

I've purged the page cache at that location, and I don't see any issues when viewing it. KormiSK, if you're still seeing that content, you likely need to clear your browser cache. ~Oshwah~^{(talk) (contribs)} 00:15, 10 May 2024 (UTC)

Stale request at MediaWiki talk:Gadget-watchlist-notice-core.js

Could an interface admin please handle the very old request at MediaWiki talk:Gadget-watchlist-notice-core.js? Thanks. * Pppery * _{it has begun...} 16:37, 19 May 2024 (UTC)

Using console.log instead of comments to blank user scripts

Example of a user script that a consensus at IANB caused to be blanked: User:Technical 13/Scripts/OneClickArchiver.js

Would it make more sense to console.log the blanking message rather than adding a comment? Would give the end user more of a hint as to what happened and what needs to be upgraded. –Novem Linguae (talk) 17:07, 22 May 2024 (UTC)

I guess so, but given that anyone who knows enough to look at the javascript console will presumably know to also look at the script source to see what's going on, this feels like it'd be more trouble than it's worth. Since it's not really much of a use case, I think I'd personally prefer to keep using comments instead, for simplicity's sake. Writ Keeper ⚇♔ 17:24, 22 May 2024 (UTC)

Changing // to console.log seems fairly simple to me. Having a non-silent error seems better than a silent one to me. –Novem Linguae (talk) 17:33, 22 May 2024 (UTC)

"Simple" from the perspective of not making an editor's browser do more than it needs to, even if it's just a logging statement. If it's not going to actually help anyone, why do it? Writ Keeper ⚇♔ 17:47, 22 May 2024 (UTC)

I see giving users a hint as to why their user script broke as superior to failing silently. No worries if you disagree though. –Novem Linguae (talk) 18:01, 22 May 2024 (UTC)

If we had some extremely popular script, it could be part of the deprecation process, but agree with WK - the number of people that even know how to open their jslog is exceptionally low. — xaosflux ^Talk 18:25, 22 May 2024 (UTC)

I agree with Novem Linquae - it will help some small subset of the population and hurt nobody so there's no reason not to do it. But this is a bridge best crossed when it happens, as Technical 13's script has been blanked long enough that everyone who needs to know has known already. * Pppery * _{it has begun...} 18:33, 22 May 2024 (UTC)

What about mw.notify? Obviously it'd be fairly intrusive to have it on every page. — Qwerfjkltalk 20:04, 22 May 2024 (UTC)

Yeah, def a no-go, and not worth doing shenanigans like 1/1k or 1/10k chance. ~ Amory (u • t • c) 22:53, 22 May 2024 (UTC)

I think the point being made there is that for the overwhelming majority of users, checking the JS console in their browser is not the first port of call; a comment on the page itself is probably much more of a hint since most folks are far more likely/able to do do so. Putting a message in a console log is, for most, more akin to "failing silently" than a comment.

At any rate, clearly the answer is both. ~ Amory (u • t • c) 22:50, 22 May 2024 (UTC)

I am almost always going to check the devtools js console before i go reading program code. But there's no support for my idea so i withdraw it. No worries. –Novem Linguae (talk) 23:46, 22 May 2024 (UTC)

I'm not going to stop someone adding console.log if they're the ones who are blanking a script, but I also don't want to be required to do so myself. Izno (talk) 00:04, 23 May 2024 (UTC)